home *** CD-ROM | disk | FTP | other *** search
- Path: chronicle.mti.sgi.com!news
- From: fjh@munta.cs.mu.OZ.AU (Fergus Henderson)
- Newsgroups: comp.std.c++
- Subject: Re: Throwing an exception from within a signal handler
- Date: 09 Jan 1996 18:27:24 GMT
- Organization: Computer Science, University of Melbourne, Australia
- Approved: austern@mti.sgi.com
- Message-ID: <9601003.29971@mulga.cs.mu.OZ.AU>
- References: <4cpmh0$ltf@natasha.rmii.com> <Etay_Bogner-0901961008510001@metay.stil.scitex.com>
- NNTP-Posting-Host: isolde.mti.sgi.com
-
-
- Etay_Bogner@mail.stil.scitex.com (Etay Bogner) writes:
-
- >In article <4cpmh0$ltf@natasha.rmii.com>, jtc@rmii.com (Jim Cochrane) wrote:
- >
- >>> Does the proposed ANSI standard say anything about throwing an exception
- >>> from within a signal handler?
-
- No.
-
- >>> Is the resulting behavior safe and
- >>> well-defined, or is it undefined or implementation-dependent?
-
- Because the draft standard doesn't say anything about it,
- I guess it is implicitly undefined behaviour.
-
- >Again, I wonder why this passed the moderation ...
- >
- >signal handlers is a C++ issue ? come on ...
-
- I think the issue of whether the standard says anything about *Foo* is
- generally appropriate to comp.std.c++, even if the answer is "No.", and
- the resulting discussion rather short.
-
- P.S. Probably Etay Bogner's meta-post should not have got past moderation ;-)
- As a reminder, comments on the moderation policy should be addressed
- c++-std-request@ncar.ucar.edu.
-
- --
- Fergus Henderson WWW: http://www.cs.mu.oz.au/~fjh
- fjh@cs.mu.oz.au PGP: finger fjh@128.250.37.3
-
-